Information standards

This section sets out the standards, methods, and procedures that apply to the production, exchange, and management of information on this project. All appointed parties shall comply with these requirements when creating, sharing, and delivering information.

Use this section to confirm the project’s approach to standards, tools, formats, and CDE processes. Provide a realistic project-specific answer.

Information management standards

Information shall be managed in accordance with recognised international and national standards to ensure consistency, traceability, and interoperability.

Function Standard Description
Information management ISO 19650 series Collaborative production and management of information across the project lifecycle
National Annex {{Local Annex}} (e.g. UK National Annex) National guidance applicable to the project location
Classification {{Classification system for this project}} (e.g. Uniclass 2015) Classification system used to structure models, documents, and scope
Level of Information Need ISO 7817-1 Method for defining information requirements by purpose, stage, and use
Asset management ISO 55000 series Principles for managing information required for asset operation
Open data & model exchange ISO 16739 (IFC) Open, neutral data format for interoperable exchange of model-based information.
Information delivery planning ISO 29481 (IDM) Framework for defining information delivery processes, exchanges, and responsibilities.
Data structure & dictionaries ISO 23386 / ISO 23387 Standards for defining data dictionaries and data templates.
Information containers & linking ISO 21597 (ICDD) Method for structuring, linking, and managing information containers.
Drawings & representation ISO 4157 Standards governing construction drawings and building representation.
GIS–BIM interoperability ISO 23262 (If applicable) Requirements for interoperability between GIS and BIM datasets.

Information Container / File Naming Standard

The naming structure aligns with ISO 19650 principles and supports automated tracking, version control, and information status management within the CDE.

Example: ABC123–IBL-A1–01–M–A-0001_BLDG1
Project Originator Functional Spatial Form Discipline Number Description
ABC123 IBL A1 01 M A 0001 _BLDG1

Geometry and Reliability Definitions

Geometry and reliability definitions clarify what level of detail is provided and how much confidence can be placed in the information:

  • Geometry may be symbolic or generic at early stages, progress to detailed elements for coordination, and reach fabrication-level detail where components are suitable for manufacture and installation.
  • Reliability reflects information maturity, ranging from preliminary assumptions, through proposed and coordinated information, to verified as-built data validated against site conditions.

These definitions help ensure information is used appropriately for coordination, construction, and handover, reducing misinterpretation and rework.

Why this matters

Clear standards for naming, geometry, and reliability reduce ambiguity, prevent misuse of information, and support consistent verification. This enables teams to trust the information they receive and ensures models and data can be confidently used for coordination, construction, and handover.